---

Creating a Master-Detail Interface

1. Prepare the nib file.

   In Interface Builder, delete the table view from the window.

   Delete the Studio EODisplayGroup and the EditingContext from the nib file window.

   Save the nib file.

2. Set the window title.

   Select the window by clicking its title bar.

   Choose Inspector from the Tools menu.

   Enter "Studio Manager" in the TItle field of the Attributes display.

   

   You can create a master-detail interface by simply dragging a relationship from EOModeler onto your window.

3. Create a master-detail interface.

   Drag Studio's movies relationship from EOModeler onto the window in Interface Builder.

   Rearrange and resize the tables so that they are next to each other.

   Reconnect the Add and Remove buttons to the new Studio EODisplayGroup

   Reconnect the Save button to File's Owner (the interface controller).

   (See Adding Action Methods for these procedures.)

   

   This operation creates a master-detail interface. Columns are automatically added for all of the attributes marked as class properties; you can delete any columns you don't want.
   For a Java Client application, the interface controller--represented by the File's Owner icon in the nib file window--is the "controller" object in the Model-View-Controller design scheme. The interface controller comes already connected to its "view" through the component outlet. But you must connect it to its "model" object, the editing context.

4. Connect the interface controller to its editing context and display group.

   Control-drag from File's Owner to the EditingContext icon in the nib file window.

   In the Connections inspector, select the editingContext outlet.

   Click Connect.

   

   Control-drag from File's Owner to the Studio icon in the nib file window.

   In the Connections inspector, select the displayGroup outlet.

   Click Connect.

   In the following figure, you can see the master-detail interface in action. Notice that the table views have been rearranged, and that titles have been added above the Studios and Movies tables.

5. Test your interface.

   Choose File Test Interface.

   

6. Use Project Builder to build the application.

   To see the effects of your changes, you must compile and run the application. However, before you run the application, there is one last step to perform. The applet providing the running environment for your Java Client application is set to a default size in the WOJavaClientApplet bindings in Main.wod. This size could be too small to accommodate your user interface (or too large for it).

7. Learn the size of the window.

   Open StudioManager.nib.

   Choose Inspector from the Tools menu.

   Select the Size inspector.

   Write down the w and h parameters.

   

   For example's sake, let's assume the window is 503 pixels high and 700 pixels wide. Transfer these numbers to the WOJavaClientApplet.

8. Set the WOJavaClientApplet size bindings.

   Open Main.wod.

   Enter the dimensions of the window in the height and width bindings.

   Save the file.

   Applet: WOJavaClientApplet {
     height = 503; // change this
     width = 700; // and this
     interfaceControllerClassName =
   "studiomanager.client.StudioManager";
     useJavaPlugin = NO; }

   Now you are ready to test the application.

9. Run and test the application.

   Choose Tools Launcher Run to launch the server side of the application.

   Start up the client side (see Running a Java Client Application ).

   When you select a studio in the Studios table view, the display changes in the Movies table view to show the selected studio's movies.